home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / urn / urn-archives / urn-ietf.archive.9611 / 000124_owner-urn-ietf _Mon Nov 11 15:24:32 1996.msg < prev    next >
Internet Message Format  |  1997-02-19  |  2KB

  1. Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id PAA09890 for urn-ietf-out; Mon, 11 Nov 1996 15:24:32 -0500
  2. Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id PAA09885 for <urn-ietf@services.bunyip.com>; Mon, 11 Nov 1996 15:24:28 -0500
  3. Received: from fssun10.dev.oclc.org by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
  4.         id AA25687  (mail destined for urn-ietf@services.bunyip.com); Mon, 11 Nov 96 15:24:20 -0500
  5. Received: from orc.NISOR (orc.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
  6.     id AA00924; Mon, 11 Nov 96 13:55:10 EST
  7. Received: by orc.NISOR (SMI-8.6/SMI-SVR4)
  8.     id NAA20145; Mon, 11 Nov 1996 13:56:14 -0500
  9. Date: Mon, 11 Nov 1996 13:56:14 -0500
  10. From: stu_weibel@oclc.org (Stu Weibel)
  11. Message-Id: <199611111856.NAA20145@orc.NISOR>
  12. To: urn-ietf@bunyip.com
  13. Subject: Re: [URN] I18N does not belong in URNs
  14. X-Sun-Charset: US-ASCII
  15. Sender: owner-urn-ietf@services.bunyip.com
  16. Precedence: bulk
  17. Reply-To: stu_weibel@oclc.org (Stu Weibel)
  18. Errors-To: owner-urn-ietf@bunyip.com
  19.  
  20. > From owner-urn-ietf@bunyip.com Mon Nov 11 13:22:32 1996
  21. > Errors-To: owner-urn-ietf@bunyip.com
  22. > Errors-To: owner-urn-ietf@bunyip.com
  23. Keith Moore writes:
  24.  
  25. > URNs aren't supposed to be human-meaningful.  Making them human-meaningful
  26. > defeats the purpose of having them be long-term stable.
  27.  
  28. This reflects a philosophy, an attitude, a point of view that is NOT
  29. shared in anything like a consensus in this group.  I say again...
  30. this WG should adopt the *least restrictive* solution that is technologically
  31. sound and let people do with it what their communities choose.  
  32.  
  33. This group has no business enforcing naming philosophy on the applications
  34. or systems that will deploy URN solutions.
  35.  
  36. stu
  37.  
  38.